Fixes #3367

Fixes stupid behaviour of Laravel again... Matthias would be proud. 😃

In theory we should use the $request->hasCorrectSignature() method here. However, for some stupid unknown reason, the path value is added to the server Query String. This completely invalidates the signature check.
For example the url http://localhost:8000/image/small2x/c3/3d/c661c594a5a781cd44db06828783.png?expires=1748380289
will be verified as : http://localhost:8000/image/small2x/c3/3d/c661c594a5a781cd44db06828783.png?/image/small2x/c3/3d/c661c594a5a781cd44db06828783.png&expires=1748380289
which makes the signature check fail as the hmac does not match.

Tested to work locally on my docker compose install.

Enhancements to secure image links:

• Added SignatureExpiredException: Introduced a new exception class SignatureExpiredException to handle cases where a secure link's signature has expired.
• Refactored signature validation logic: Updated the SecurePathController to differentiate between invalid and expired signatures, logging detailed errors for invalid cases and throwing appropriate exceptions. Added private methods hasCorrectSignature and signatureHasNotExpired to encapsulate these checks.
• Improved URL generation: Enhanced the pathToUrl method in HasUrlGenerator to handle cases where signed URLs are not used, ensuring compatibility with secure image link configurations.

Expanded test coverage:

• New test cases for secure links: Added tests for expired signatures (testExpiredSignature) and broken signatures (testBrokenSignature) to validate the new exception and logic. Refactored existing tests to use helper methods for enabling secure and temporary links. [1] [2] [3]
• Refactored test setup: Introduced helper methods setSecureLink and setTemporaryLink in SecureImageLinksTest to streamline test configuration and improve clarity.